User

I have (and probably others) been using Compustar T11/T12-type remotes on an EVO-ONE without issue, even though this isn't an officially supported configuration. Now Compustar has the Pro T13. I bet this would work also, but I don't feel like being the guinnea pig, but I'd certainly like to use this remote -- So, has any installer tried this yet?

What is the maxiumum current (mA) I can draw from the +12V line in the shock sensor port of an EVO-ONE? Thanks, Jeff

I'm not a Fortin rep but someone might find this useful -- I struggled with making these types of Compustar remotes work with the EVO-ONE. There are a few reports here of success with these remotes, and I had to do alot of experimentation to get satisfactory results, because these reports were somewhat vague and didn't cite which Firmware revisions were used when these observations were made. I can report that Firmware 7.1.24 (latest as of this thread) allows full function of these remotes without any drama, with the exception of a missing "remote start ready" (engine icon) indicator, which to me isn't any type of deal-breaker considering the capabilities of these units. Temperature, voltage, trunk, remote valet, alarm paging, etc. all work. The Fortin documentation states that FW 7.0.96 must be flashed for (supported) Compustar remotes, but this FW level is not sufficient to get full function from the (unsupported) T11/T12 remotes. 7.0.96 - Couldn't program remotes with Mode 1 or Mode 5. 7.1.16 - Remotes programmed immediately on Mode 5 and function, but temperature and voltage status reported erroneous numbers. 7.1.24 - Remotes programmed immediately on Mode 5 and all functions appear to work, with the exception of the "ready" engine icon which indicates a remote start is possible. IMHO, might be an issue for manual-transmission vehicles. Remote start functions regardless. To get this remote to work, flash the EVO-ONE to 7.1.24, and program the remotes with Mode 5. That's it. ** IMPORTANT ** -- There's no LED or valet switch on the antenna, even though the plastic housing looks like these features are there. This seriously confused me. I was trying to press that plastic square over-and-over thinking this was a valet switch, but it's a cosmetic feature, and does nothing, and there's no LED. I had to pop the antenna open to confirm this. Just flash to 7.1.24 and follow the instructions in the Compustar document from Fortin to program the remotes using Mode 5.

I'm not a Fortin rep but someone might find this useful -- I wanted to interface a flashing LED to an EVO-ONE, and didn't want to use something like a "dummy" flashing 12V LED as this doesn't properly convey the status of the unit (arming/armed/valet) and my antenna doesn't contain it's own LED. I ended up aquiring the following -- 1- RFAXL202 kit, which is a pair of harnesses used to interface DEI anetnnas to the EVO-ONE with an XL-202. 2- A DEI 2v "super-bright" LED (either the red or blue ones. The blue LED is several orders of magnitude brighter than the red at the same 2v, if that's what you want). 3- A 220ohm resistor. The RFAXL202 kit contains a four-pin blue plug with a single orange wire. I de-pinned the orange wire on the Fortin plug and inserted the pin from the DEI LED connected to the blue wire on the DEI LED in its place. I insertered the pin on the DEI LED connected to the red wire into the Fortin plug directly adjascent to the blue DEI wire that replaced the orange wire. I put a 220ohm resistor in series on the red wire on the DEI LED. The resistor is necessary because the EVO-ONE is outputting 5V on the pin used by the red wire and the DEI LED operates at 2V. This new plug will go into the larger of the two blue 4-wire plugs. This will give a functional status LED that mimicks what would be found on an antenna or a conventional car alarm. You can use a 12V, non flashing LED and simply connect the (-) to the orange wire on the blue plug from the RFAXL202, but I think this method of interfacing the LED is cleaner, and I find the appearance of the DEI LED housings to be aesthetically superior to a generic 12V LED when installed into a blank panel, etc. in a vehicle.

Is there any telematics module that I can use on an EVO-ONE that has a Compustar remote? EDIT: The Compustar remote is connected to the smaller 4-pin blue plug, where most of the telematics modules also connect.

EVO-ONE, 2017 Civic Coupe with manual, regular key and T-Harness. Is there any way to wire in a switch to disable the remote starter, for example if parked in a garage for extra safety?

Hi all! I'd like to know recommended wire splicing method. I'm electrician and just got Evo-All and Flash-link plus separate remote starter to go into my wife's 2010 RAV4 (it has a dot on the key so no Evo-One for me...) Is soldering the best way? And then heat shrink? Or there is a better way? Thanks!!!

I have an EVO-ONE installed in a 2017 Civic LX coupe, conventional key, manual trans, with T-harness (THAR-ONE-HON2 12-B1). The remote-start/bypass/alarm all work properly. It's my understanding the brown wire on the T-harness (the one with the fuse) from the ignition harness can be used for a siren. What settings do I need to enable to make this work? Right now, when the siren is connected and I crank the car the siren goes off continuously. Thanks, Jeff

This is more of anwsering my own questions that I had prior to installing my system. I have an eve-one installed and a compustar t11 & g15 pro rf kit. Both remotes programed as expected with the lock button. The g15 pro works 100% as expected, aside from not sounding off when the alarm is set off (but that's how it's supposed to work). On the t11 remote the voltage and temprature work great. The only thing that doesn't work as expected on the t11 is the engine icon, which should be lit when the car is able to be remote started, is not lit. The car still remote starts, you just dont get the engine icon that says it's ready to be started. In all though the compustar t11, g15 pro and the ant-2wdss antenna work great with the evo-one.